|
|
DWF_DC_01 - Partitions cycles check |
|---|---|
| This validation rule ensures that a partition of an element cannot have a partition typed by this element. Thus it avoids"partitions cycles". | |
|
|
DWF_DC_02 - Role Allocation |
|---|---|
| This rule checks the role allocations consistency between roles and entities. | |
|
DWF_DC_03 - Physical Path Involved Links check |
|---|---|
| This rule checks that a PhysicalPath is valid. | |
|
|
DWF_DC_04 - Check multiple deployment |
|---|---|
| This rule depends on the Preference option "Multiple deployment allowed". If this option is set to false, the rule checks that a Behavior Physical Component is not deployed on more than one Node Physical Component. | |
|
|
DWF_DC_05 - Part type accessibility check |
|---|---|
| This rule ensures that a part is typed by an accessible Component. | |
|
|
DWF_DC_06 - Component Parts type level check |
|---|---|
| This rule ensures that each parts of a component have the same level (i.e context, logical, physical,...) that the component itself. | |
|
|
DWF_DC_07 - Part typed by an Abstract Type |
|---|---|
| This rule checks that a Part is typed by an abstract type. | |
|
|
DWF_DC_08 - Part typed |
|---|---|
| This rule ensures that a part has always a type. | |
|
|
DWF_DC_09 - Component allocated functions types check |
|---|---|
| This rule checks that a Component allocates only leaf Functions of its own level. | |
|
|
DWF_DC_11 - Component Functional Allocation |
|---|---|
| This rule checks the allocation level consistency between functions and components to avoid allocations of system functions in logical architecture. | |
|
|
DWF_DC_12 - Function Allocation Unicity |
|---|---|
| This rule checks that a function is allocated to only one component (including Actor) | |
|
|
DWF_DC_13 - Component Exchange Functional Exchanges Realization |
|---|---|
| This rule checks that the Functional Exchanges allocated to a Component Exchange come from the same level. | |
|
|
DWF_DC_14 - Component Port Allocation |
|---|---|
| This rule checks Ports Allocations consistency. | |
|
|
DWF_DC_15 - Function Allocation Consistency |
|---|---|
| This rule checks that only leaf functions are allocated. | |
|
|
DWF_DC_16 - Component Exchange encapsulation problem check |
|---|---|
| This rule raises a warning if a Component Exchange is linked between two internal components. These components can be directly connected, only if the ports are delegated throughout the owning components which are connected by another Component Exchange. | |
|
|
DWF_DC_17 - Component self generalization not allowed |
|---|---|
| This rule ensures that a Component cannot generalize itself. | |
|
|
DWF_DC_18 - Component Exchange location check |
|---|---|
| This rule ensures that Component Exchange is located in the common ancestor between its source/target elements. | |
|
|
DWF_DC_19 - Physical Link location check |
|---|---|
| This rule ensures that Physical Link is located in the common ancestor between its source/target elements. | |
|
|
DWF_DC_20 - Physical Component Function Allocation check |
|---|---|
| This rule ensures that Physical Component of nature NODE does not allocate any Function. | |
|
|
DWF_DC_21 - PhysicalComponent check deployment/containment of Sub-PhysicalComponents |
|---|---|
| This rule ensures that PC is correctly deploying/containing other child PC.
Node Components (actor or not) can contain Node and deploy Node or Behavior. Behavior Components (actor or not) can contain Behavior and deploy behavior. NodePC=Physical Component of nature NODE BehaviourPC=Physical Component of nature BEHAVIOUR |
|
|
|
DWF_DC_22 - PhysicalComponent check deployment/containment in Parent-PhysicalComponent |
|---|---|
| This rule ensures that PC is correctly deployed/contained in parent PC.
NODE PC cannot be deployed/contained by a BEHAVIOUR PC BEHAVIOUR PC cannot be contained by a NODE PC |
|
|
|
DWF_DC_24 - Physical Path involvement check involved element |
|---|---|
| This rule checks that a Physical Path Involvement only involves an Part, a Physical Link or a Physical Path. | |
|
|
DWF_DC_26 - Root Physical Component Ports Check |
|---|---|
| This rule ensures that the Root Physical Component has no physical ports. | |
|
|
DWF_DC_27 - Functional Exchange Component Exchange Allocation Unicity |
|---|---|
| This rule checks that a functional exchange is allocated to only one component exchange. | |
|
|
DWF_DC_28 - Delegation out of place check |
|---|---|
| This rule check that Component Exchange of kind Delegation if not out of place and useless.
It also make sure if Delegation source and target are not null. |
|
|
|
DWF_DC_29 - Component Exchange Functional Exchange consistency |
|---|---|
| This rule ensures that Component Exchange allocates valid functional exchanges (regarding ports directions). | |
|
|
DWF_DC_30 - PhysicalPort on BehaviourPC |
|---|---|
| This rule ensures that PhysicalPort is not contained in BehaviourPC.
BehaviourPC=Physical Component of nature BEHAVIOUR |
|
|
|
DWF_DC_31 - ComponentPort on NodePC |
|---|---|
| This rule ensures that ComponentPort is not contained in NodePC.
NodePC=Physical Component of nature NODE |
|
|
|
DWF_DC_32 - Component Exchange with out port on NodePC |
|---|---|
| This rule ensures that ComponentExchange with out port sourceEnd or target end is not NodePC.
NodePC=Physical Component of nature NODE |
|
|
|
DWF_DC_33 - PhysicalPath allocated CE |
|---|---|
| This rule checks that a PhysicalPath should allocated component exchage between its path. | |
|
|
DWF_DC_34 - PhysicalComponent of nature UNSET |
|---|---|
This rule ensures that a Physical Component is not of nature UNSET, with the exceptions below, in which UNSET is allowed:
1. Only root Actors (inside structure) can be nature UNSET
2. The root Physical Component can be nature UNSET
|
|
|
|
DWF_DC_35 - Function is not available in at least one Mode/State allocated to a functional chain in which the function is involved |
|---|---|
| Check that the function is available in all the Mode/State allocated to a functional chain in which the function is involved. | |
|
|
DWF_DC_36 - Component or Actor compositions checks |
|---|---|
This rule checks Component or Actor composition following the rules below:
1. Component or Actor with the 'is Human' flag set on true cannot have sub Components, sub Actors, also no contained Parts or managing sub-packages.
2. An Operational Actor cannot be decomposed.
|
|
|
|
DWF_DC_37 - This rule checks that only one System Component is allowed at SystemAnalysis level |
|---|---|
| This rule checks that only one System Component is allowed at SystemAnalysis level (cannot have parts inside a System nor component type) | |
|
|
DWF_DC_38 - This rule checks that only a Root Component exists at System/Logical/Physical level |
|---|---|
| This rule checks that only a Root Component exists at an Architectural level. Zero or more than one Root Components are not allowed. | |
|
|
DWF_DC_39 - PhysicalSystem should be of nature UNSET |
|---|---|
| This rule ensures that the PhysicalSystem Component is of nature UNSET. | |
|
|
DWF_DC_40 - This rule checks that an Operational Entity is not HUMAN |
|---|---|
| This rule checks that an Operational Entity is not HUMAN. | |
|
|
DWF_DC_41 - This rule checks that an Operational Actor is HUMAN |
|---|---|
| This rule checks that an Operational Actor is HUMAN. | |
|
|
DWF_DC_42 - Component with parts |
|---|---|
| This rule ensures that a component is always referenced by at least one part. | |
|
|
DWF_DC_43 - Component Exchange has an UNSET Kind |
|---|---|
| Check if the Component Exchange has an UNSET kind. | |